sys_fs: Fixed up sys_fs_fcntl(0xc0000007, 0xc0000015, and 0xc000001c) according to real hardware testing #14368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tested
sys_fs_fcntl(0xc0000007)
akacellFsArcadeHddSerialNumber
on my real hardware, validated the result, and compared the output values with the ones obtained from some other methods on my PC.It turned out that padding and alignment (model: left, serial: right) are used by
sys_fs_fcntl(0xc0000007)
to compose the output.Following is the information of my HDD obtained through
sys_fs_fcntl(0xc0000007)
for example:Also, it seems like the syscall doesn't care about the device name in the arguments, though it's supposed to be "CELL_FS_IOS:ATA_HDD".
I also tested
sys_fs_fcntl(0xc0000015&0xc000001c)
on my real hardware, and it turned out the error handling was a little bit different.Following is the testing result on the real hardware: